Prometheus endpoint (no new dependencies):
- GET /metrics — standard text/plain; version=0.0.4 Prometheus scrape
  target. Exposes releases_total, run_events_total, promoted_pointers_
  total, actions_total, actions_by_type{action=}, pricing_tables_total,
  schema_version. Same Bearer/loopback gate as GET /v1/metrics.
  8 new tests in tests/test_prometheus_metrics.py.
  Documented in docs/http-api.md with sample output + scrape config.

TypeScript SDK (sdk-ts/, package name: flightdeck-ai):
- FlightDeckClient: ingestEvent/s(), diff(), getWorkspace(), health()
  using native fetch (Node 18+, zero deps).
- FlightDeckOpenAIAdapter: wraps openai.chat.completions.create(),
  records tokens + latency + success as a RunEvent. Fire-and-forget.
- Types fully grounded in schemas/v1/run_event.schema.json and
  src/flightdeck/models.py. No any casts except JSON deserialization.
- Retry on 429/5xx (3 attempts, exp backoff). X-FlightDeck-Actor and
  X-Request-Id headers on every request.
- 584-line vitest suite: auth, retry, diff parsing, adapter latency,
  cached tokens, fire-and-forget ingest errors.
- sdk-ts/README.md: install + 10-line quickstart + OpenAI snippet.
- Package name flightdeck-ai matches the PyPI package.

MkDocs docs revamp (--strict build passes, 0.33s):
- docs/getting-started.md (NEW): 'demo worked, now what?' — 5-step
  guide from real release registration through promotion. The page
  that was missing for first-time users.
- docs/index.md: 'Where to start' decision table (7 rows) above Quick
  reference.
- docs/cli.md: 'Common patterns' section at top (4 copy-paste recipes:
  register+diff, CI gate, weekly health, Slack webhook).
- docs/sdk.md: 'Quickstart' section at top (50-line annotated Python
  example, end-to-end).
- docs/troubleshooting.md: 'First 5 things to check' numbered checklist.
- mkdocs.yml: Getting started added as second nav item.

Link cleanup:
- CHANGELOG.md: two GitHub blob /docs/cli.md links → hosted Pages URL.
- All other relative links left intact (GitHub renders them correctly).

Three audiences kept hitting dead ends:
- 'I want to run this for my team' → no clear Postgres path
- 'Is SQLite OK for prod?' → no guidance
- 'How do I back up?' → pg_dump mention was buried

Changes:
- docs/getting-started.md: 'Production checklist' section — Postgres
  install (pip install 'flightdeck-ai[postgres]'), database_url YAML +
  env var, Bearer token for remote access, process supervisor guidance.
- docs/operations-and-policy.md: SQLite vs PostgreSQL summary table
  near the top, links to existing detailed section.
- docs/index.md: 'Deploy for a team in production' row added to the
  Where-to-start decision table.
- examples/deploy/README.md: 'Using PostgreSQL' section with a complete
  docker-compose.postgres.yml snippet (postgres:16-alpine + flightdeck
  wired via FLIGHTDECK_DATABASE_URL).